Providing services in a data storage system

ABSTRACT

A catalog of services defines which storage-related services are applied to each service level of storage where storage capacity is managed and allocated in terms of chunks of capacity at different service levels. Each service level is defined based on one or more of tiered storage policy settings, drive size, drive speed, drive count, RAID protection, engine fractions, bandwidth and availability and characterized by one or more performance capabilities. Examples of services in the catalog include but are not limited to mobility, availability, continuity, and recovery services. Any combination of services, or no services at all, can be associated with a given service level of storage. Services may be performed at different performance levels. Further, services may be provided on-demand and billed on a usage basis.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of pending U.S. patent application Ser.No. 13/836,185 titled PROVIDING SERVICES IN A DATA STORAGE SYSTEM, whichwas filed on Mar. 15, 2013.

BACKGROUND OF THE INVENTION

The invention is generally related to electronic data storage systemswhich are associated with a network. Enterprise and service providerdata storage systems are used to maintain relatively large data sets. Asimple data storage subsystem includes a storage array and a hostdevice. Applications Read and Write data by sending IO requests to thehost device via the network. The host device translates the IO requestsfrom a format characterized by designators used by applications, e.g.,filename, into a format characterized by designators used by the storagearray, e.g., LUN, cylinder and track, in order to prompt a Read or Writein accordance with the IO request. Clusters of hosts and storage arrayscan be organized into a data center. Groups of data centers can beorganized into a single data storage system. A wide variety oftechnologies are known for preventing interruptions of businessoperations due to data storage problems. However, the costs associatedwith these technologies tend to increase in relation to increases indata storage capacity and other factors. Moreover, some of the resourcesrequired to implement these technologies are only used in the event ofan emergency and associated costs may be difficult for an enterprise orservice provider to justify if the probability and cost of a particulartype of data storage problem cannot be accurately calculated.

SUMMARY OF THE INVENTION

In accordance with an aspect an apparatus comprises: a data storagearray having a plurality of physical data storage devices which define adata storage capacity of the storage array, the data storage devicesincluding at least first and second storage devices characterized bydifferent performance metrics; a first data record which associateschunks of the data storage capacity of a predetermined size with ones ofthe physical storage devices, and which indicates a service level forthe chunks, wherein there are multiple service levels and each servicelevel is indicative of a level of performance; a second data recordwhich associates a service with at least one of the service levels; andlogic which performs the service on data stored at the service levelwith which the service is associated.

In accordance with another aspect a method comprises: in a data storagearray having a plurality of physical data storage devices which define adata storage capacity of the storage array, the data storage devicesincluding at least first and second storage devices characterized bydifferent performance metrics, associating chunks of the data storagecapacity of a predetermined size with ones of the physical storagedevices; associating each chunk with a service level of a plurality ofservice levels indicative of different levels of performance; allocatingchunks of data storage capacity at each service level; associating aservice with at least one of the service levels; and performing theservice on data stored at the service level with which the service isassociated.

An advantage associated with some aspects is extending a service catalogto enable association of different sets of services with different setsof storage capacity characterized by levels of service. As described inU.S. patent application Ser. No. 13/609,398, titled SERVICE LEVEL BASEDDATA STORAGE, filed contemporaneously herewith and incorporated byreference, the data storage capacity of a storage array, data center ornetworked data storage system can be managed and allocated in terms ofchunks of capacity at different service levels, where each service levelis defined based on one or more of tiered storage policy settings, drivesize, drive speed, drive count, RAID protection, engine fractions,bandwidth and availability and characterized by one or more performancecapabilities, e.g., IOs per second. A catalog of services defines theservice levels and storage-related services that may be applied to eachservice level. Examples of services include but are not limited tomobility, availability, continuity, and recovery services. Anycombination of services, or no services at all, can be associated with agiven service level of storage. Consequently, each service level can beassociated with a unique set of services. Moreover, the services may beprovided at different levels. For example, a recovery point servicecould be characterized by level parameters such as a recovery pointobjective (RPO) and recovery time objective (RTO). The enterprise mayspecify the services to be associated with each service level of storageand also the level of the service if multiple levels are defined.Moreover, billing may be based on the one or more of service level ofstorage, service associated with the service level of storage, and levelof service, each of which may be at a specified cost per unit ofstorage.

Another advantage associated with aspects of the invention is providingservices on-demand and billing based on usage. The resources required toimplement some services are relatively costly and may increase as afunction of data storage capacity. Moreover, some of the resourcesrequired to implement these technologies are only used in the event ofan emergency. By providing services on-demand and billing on a usagebasis the costs to a service provider or enterprise can be reduced.

Other features and advantages will become apparent in view of thedetailed description and figures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a “cloud” environment in which a storage vendormanages provision of various services to a service provider orenterprise.

FIG. 2 illustrates a data center in greater detail.

FIG. 3 is a functional block diagram of the storage vendor device.

FIG. 4 is a block diagram which illustrates service invocation andbilling.

FIG. 5 is a flow diagram which illustrates service invocation andbilling.

DETAILED DESCRIPTION

Some aspects of the invention may be partially or wholly implemented inone or more computer programs. The computer programs are stored onnon-transitory computer-readable memory and implement processes whichmay be defined by steps when utilized by general processor, specializedprocessor, or combination of processing devices.

FIG. 1 illustrates a “cloud” environment in which various computingdevices utilize a data storage system via a network 100. The computingdevices may include, for example and without limitation, servers 102,personal computers 104 and handheld mobile devices 106. The data storagesystem may include, for example and without limitation, data centers108, 110, which may be operated by an enterprise or service provider(hereafter the example of a service provider is used). Data centers 108,110 may be configured such that storage resources associated with thedifferent data centers are presented and utilized as a single logicalset 114 of storage resources including hosts and logical volumes fromthe perspective of the computing devices. Until recently the assets ofdifferent data centers were not integrated in a manner which supportedsuch a presentation of resources. EMC VPLEX differs from such typicalprior art systems because it enables federation of information acrossmultiple data centers such that hosts and volumes located in differentdata centers function as if located in the same data center, at leastfrom the perspective of a client application. Such federation isadvantageously practical even where the distance between the datacenters is so great that synchronous Write IOs would result inun-acceptable delay because in at least some configurations the systemhas active/active asynchronous capability, e.g., a volume can be sharedby two VMs located at different data centers at distances typicallyassociated with asynchronous topologies. Data center 112, which may beoperated by a storage vendor or a third party, could also contributeresources to the single logical set 114. As will be explained in greaterdetail below, a service management device 116 coordinates availableresources in order to provide various storage-related services to theservice provider, and those service may be provided using the singlelogical data set 114. Moreover, different services may be associatedwith particular service levels of storage.

The logical set of storage resources is organized and managed based onservice levels (Levels 0 through 2 in the illustrated example), whereeach service level is indicative of a particular level of performance.For example, each service level might be characterized by a minimumlevel or range of performance measured in terms of IO operations perunit time that can be performed, e.g., Level 0 being characterized bybest performance in terms of IOs per second, Level 2 being characterizedby lowest performance in terms of IOs per second, and Level 1 beingcharacterized by performance between that of Level 0 and Level 2 interms of IOs per second. Other differentiators which could be associatedwith service levels include but are not limited to media type (e.g.,flash, phase-change memory (PCM), magnetic, etc.), rotational speed(e.g., 15K rpm, 10K rpm, 7.2K rpm, 5.4K rpm, etc.) and data protectione.g., (RAID-1, RAID5, RAID-6, erasure coding, etc.). An authorized useror storage manager can allocate and de-allocate chunks of storageresources of a predetermined size at a particular level to an entity,where the entity may be an application, type of application, user, typeof user, user group, device, type of device, or any other identifiableconsumer of storage resources.

FIG. 2 illustrates an exemplary data center 199 in greater detail. Theexemplary data center could serve as a service provider data center or astorage vendor data center. The exemplary data center includes at leastone cluster 200 of physical server devices 202 ₁ through 202 _(n)(hosts) and at least one cluster 206 of one or more data storage arrays204 ₁ through 204 _(n). The hosts and data storage arrays are typicallyin communication via high bandwidth links. In general, the data storagearrays respond to IO requests from the hosts. Each host may supportmultiple instances of virtual hosts (virtual machines), and the datacenter is configured to selectively enable any virtual machine toutilize the storage resources of any storage array. The data center alsoincludes a monitoring and service invocation function. The monitoringand service invocation function monitors resource utilization and isresponsive to signals from devices inside or outside the data centerindicating a need for a service.

FIG. 3 is a functional block diagram of the storage vendor device 116.The storage vendor device may include a server with software including aprovisioning module 904, a billing module 902, and a catalog of services906. The provisioning module 904 functions to provision storage-relatedservices which are listed in the catalog of services 906. The billingmodule 902 functions to calculate billing data associated with servicesselected by or provided to the service provider by the storage vendor.The catalog of services, which may be implemented on one or more linecards, includes data records 907 indicating which storage resources areassociated with each service level and the amount of storage capacityallocated at each service level, and data records 908, 910, 912, 914,916 that indicate which services are associated with the various servicelevels. Examples of services include but are not limited to migration,mobility, availability, continuity, and recovery. The customer chooseshow to extend the base service catalog with the additional availabilityfeatures. Logic for implementing the services may be distributed onvarious devices including device 116. Mobility service might includemoving data to a different logical or physical device within a storagearray, moving data to a different storage array, and moving hosts(instantiating new VMs on other servers which may be at the same datacenter or a different data center). Availability service might includemultiple active copies of a data set. Continuity service might includesnaps, clones and other procedures related to backup and protection.Recovery service might include recreating hosts and data sets at analternate site. In the illustrated example data record 908 indicatesthat mobility service is associated with storage capacity at servicelevel 0. Consequently, data stored at service level 0 is moved whennecessary by the mobility service logic. The mobility service is notassociated with service levels 1 and 2 so data stored at those servicelevels is not moved by the mobility service. Any combination ofservices, or no services at all, can be associated with a given servicelevel of storage. The services may also be provided at differentperformance levels. For example, Levels A and B of a recovery pointservice could be characterized by different performance level parameterssuch as recovery point objective (RPO) and recovery time objective(RTO). The recovery point objective defines the amount of data that theservice provider is willing to lose in the event that a system has to berecovered. The recovery time objective defines the amount of timeallowed for a system or application to be recovered and fully functionalfor use by the service provider. The enterprise may specify the level ofthe service to be provided to the storage service level if multiplelevels of service are defined. In the illustrated example Level Arecovery service is associated with storage capacity at service level 1.Moreover, the source and target side may be at different service levels.

FIGS. 4 and 5 illustrate service invocation and billing. Billing may bebased on one or more of service level of storage, service associatedwith the service level of storage, and level of service, each of whichmay be at a specified cost per unit of storage. An initial step 600 isto detect a need for a service. The need for a service can beautomatically identified by the monitoring and service invocation module912 of data center 108, or manually identified via operator input 500.The service invocation module may utilize a wide variety of knowntechniques to automatically recognize the onset or occurrence of astorage-related problem. To provide an example with context, a need formobility because of an impending natural disaster at the geographicallocation of data center 108 could be recognized by an operator. Inresponse, the operator could manually input an indication of the need tomigrate hosts and data to a different geographical site. In step 602 anindication of the requested service is provided by the serviceinvocation module 912 of data center 108 to the provisioning module 904of storage vendor device 116. The provisioning module assesses therequest to determine whether the service is associated with the storageservice level at which the data is stored and calculate the resourcesrequired to satisfy the request in step 604. If the service isassociated with the storage service level at which the data is storedthen the provisioning module locates the required resources in step 606.Locating the resources may include signaling to the monitoring modulesof one or more data centers to determine current and projected resourceavailability. However, the monitoring modules of various data centersmight signal resource availability to the provisioning module of thestorage vendor device in order to facilitate resource location. Theinformation about available resources is used by the provisioning moduleto select resources to provide the service. In this example data andhosts are being migrated away from data center 108 so resources at sitesother than data center 108 are selected, but in practice the resourcesfor certain services might be located in the data center which issuedthe request. The provisioning module then signals to devices associatedwith the selected resources to allocate the resources in step 608. Thedevices may respond with acknowledgments. The monitoring and serviceinvocation modules of data center 108 and the other data centersassociated with provision of the service then initiate and monitor theservice in Step 610. The billing module calculates billing data for theservice in step 612. The monitoring and service invocation modules alsocoordinate to terminate the service when appropriate in step 614. Unlikeprevious arrangements wherein the resources required for instantiating aservice were leased or sold to a service provider in advance of use, thepresently described system allows the service provider to purchaseservices on demand, e.g., when there is a need for the service. However,the services need not necessarily be purchased on demand. For example,and without limitation, billing could be based on cost per unit storageat the service level and the service or services associated with thatlevel of storage.

It should be appreciated that the data storage and other resources forproviding the services may be in the service provider data centers 108,110, the storage vendor data center 110, or both. For example, datacenter 110 may be over-provisioned by the storage vendor in order tosupport on-demand services. Moreover, storage vendor data center 112 maybe used to provide on-demand services to multiple service providers.Still further, more than one data center may be utilized to provide theservice. For example, resources of storage vendor data center 112 couldbe used to augment resources of data center 108 or data center 110 inorder to provide a service to data center 110.

Any of a wide variety of billing models can be used by the billingmodule to calculate charges for the service. For example, and withoutlimitation, the service might be billed on a flat fee basis, based onthe amount and type of resources used per unit of time, or combinationsthereof. Other examples include billing based on performance requestedor provided, and based on the amount of resources utilized, e.g., costper GB. Moreover, a particular service may be billed based on theperformance level of the service provided or selected.

While the invention is described through the above exemplaryembodiments, it will be understood by those of ordinary skill in the artthat modification to and variation of the illustrated embodiments may bemade without departing from the inventive concepts herein disclosed.Moreover, while the embodiments are described in connection with variousillustrative structures, one skilled in the art will recognize that thesystem may be embodied using a variety of specific structures.Accordingly, the invention should not be viewed as limited except by thescope and spirit of the appended claims.

What is claimed is:
 1. A method for providing infrequently used emergency storage-related services to entities that lack infrastructure to perform those services, comprising: with a federated storage system that presents storage resources from a plurality of data centers as a single logical set of storage resources, performing storage-related services on-demand in response to requests from the entities, comprising: a data mobility service that comprises moving a data set from a first storage array in a first data center to a second storage array in second data center, a data availability service that comprises creating multiple active copies of the data set including creating active copies at different data centers, and a data recovery service that comprises recreating hosts at an alternate data center; and calculating separate billing for each performance of each service on a usage basis, including calculating billing for both usage of the service and utilized storage capacity.
 2. The method of claim 1 including a storage vendor utilizing resources of an enterprise or service provider data center to provide the service.
 3. The method of claim 1 including utilizing resources of a storage vendor data center to provide the service.
 4. The method of claim 1 including billing based on service level and services associated with the service level.
 5. The method of claim 1 wherein performing the storage-related service comprises moving a data set to a different storage array.
 6. The method of claim 1 wherein performing the storage-related service comprises creating multiple active copies of a data set at different data centers.
 7. The method of claim 1 wherein performing the storage-related service comprises creating a snap of a data set.
 8. The method of claim 1 wherein performing the storage-related service comprises creating a clone of a data set.
 9. The method of claim 1 wherein performing the storage-related service comprises recreating a host at an alternate site.
 10. The method of claim 1 wherein performing the storage-related service comprises recreating a data set at an alternate site.
 11. An apparatus for providing infrequently used emergency storage-related services to entities that lack infrastructure to perform those services, comprising: a federated storage system that presents storage resources from a plurality of data centers as a single logical set of storage resources, comprising a first storage array in a first data center on which a data set is stored; and a storage vendor device comprising a billing module that calculates usage-based billing data for each performance of one of a plurality of a storage-related services on the data set, including calculating billing data for both usage of the service and utilized storage capacity, wherein the storage-related services comprise: a data mobility service that moves the data set from the first storage array to a second storage array in second data center, a data availability service that creates multiple active copies of the data set, including creation of active copies at different data centers, a data recovery service that recreates hosts at an alternate data center.
 12. The apparatus of claim 11 wherein the storage vendor device comprises a catalog of storage-related services comprising information indicating association of different storage resource performance types and storage capacities with each of a plurality of service levels.
 13. The apparatus of claim 11 wherein the storage vendor device comprises a provisioning module that prompts performance of storage-related services that are listed in a catalog of storage-related services.
 14. The apparatus of claim 11 wherein the storage vendor device comprises a provisioning module that moves the data set outside the storage array in response to selection of a mobility service from a catalog of storage-related services, and the billing module calculates billing data associated with movement of the data set.
 15. The apparatus of claim 13 wherein the storage vendor device comprises a provisioning module that creates a second active copy of the data set outside the storage array in response to selection of an availability service from a catalog of storage-related services, and the billing module calculates billing data associated with creation of the second active copy of the data set.
 16. The apparatus of claim 13 wherein the storage vendor device comprises a provisioning module that creates a snap of the data set in response to selection of a continuity service from a catalog of storage-related services, and the billing module calculates billing data associated with creation of the snap.
 17. The apparatus of claim 13 wherein the storage vendor device comprises a provisioning module that creates a clone of the data set in response to selection of a continuity service from a catalog of storage-related services, and the billing module calculates billing data associated with creation of the clone.
 18. The apparatus of claim 13 wherein the storage vendor device comprises a provisioning module that uses the data set to recreate a host in response to selection of a recovery service from a catalog of storage-related services, and the billing module calculates billing data associated with recreation of the host.
 19. The apparatus of claim 13 wherein the storage vendor device comprises a provisioning module that recreates the data set outside the storage array in response to selection of a recovery service from a catalog of storage-related services, and the billing module calculates billing data associated with recreation of the data set.
 20. An apparatus for providing infrequently used emergency storage-related services to entities that lack infrastructure to perform those services, comprising: a federated storage system that presents storage resources from a plurality of data centers as a single logical set of storage resources, comprising a first storage array in a first data center on which a data set is stored; and a storage vendor device comprising: a catalog of storage-related services that are selectable for one-time performance on-demand by the entities, comprising: a mobility service that moves the stored data set outside the first storage array to a second storage array in second data center; an availability service that creates a second active copy of the stored data set outside the first storage array, including creation of active copies at different data centers; a recovery service that uses the stored data set to recreate a host at an alternate data center; and a recovery service that recreates the data set outside the first storage array at an alternate site data center; a provisioning module responsive to selection of one of the storage-related services by one of the entities to prompt a single performance of the selected storage-related service on the stored data set; and a billing module that calculates separate usage-based billing data with for each performance of each of the storage-related services on the stored data set including calculating billing for both usage of the service and utilized storage capacity. 